UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The network element must include components to proactively seek to identify web-based malicious code.


Overview

Finding ID Version Rule ID IA Controls Severity
V-34203 SRG-NET-000237-DNS-NA SV-44679r1_rule Medium
Description
A honey pot simulates multiple platforms and services used to attract and contain the attackers. To the attacker, it appears to be part of a production network providing services. A honey pot can be one or more hosts deployed within a DMZ or screened sub-net. Honey pots can be used for surveillance, as an early-warning tool, to discover security weaknesses, and to help assess threats. They also will tie up an attacker's resources as they burn time and effort. Honey pots should have no production value, and should not see any legitimate traffic or activity. Whatever they capture is malicious or unauthorized traffic. Identification of malicious code is not a function of DNS.
STIG Date
Domain Name System (DNS) Security Requirements Guide 2012-10-24

Details

Check Text ( C-42184r1_chk )
This is not a function of DNS.
Fix Text (F-38133r1_fix)
This requirement is NA for DNS. No fix required.